Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

V1.20 rc #697

Merged
merged 2 commits into from
Sep 27, 2024
Merged

V1.20 rc #697

merged 2 commits into from
Sep 27, 2024

Conversation

stephenhand
Copy link
Collaborator

Description

Checklist

  • Corresponding issue has been opened
  • New tests added
  • Feature flags / configuration added

Other Related Issues

None

Verification steps

AFTER YOU MERGE

  1. Cut a release tag using the GitHub workflow. Wait for it to complete and the notification to be posted in the #aselo-deploys Slack channel.
  2. Comment on the ticket with the release tag version AND any additional instructions required to configure an environment to test the changes.
  3. Only then move the ticket into the QA column in JIRA

You are responsible for ensuring the above steps are completed. If you move a ticket into QA without advising what version to test, the QA team will assume the latest tag has the changes. If it does not, the following confusion is on you! :-P

stephenhand and others added 2 commits September 18, 2024 08:34
…deactivate

Chi 2878 fix custom channel deactivate
* CO

* JM

* TH

* readd flex flow parameters

* add inputs

---------

Co-authored-by: Sinekhaya <[email protected]>
@stephenhand stephenhand merged commit 3479508 into master Sep 27, 2024
36 of 39 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants